Extending Functionality of Workflow applications using Instant Messaging (IM)

ABSTRACT

Plug-ins for instant messaging (IM) systems are described. By using plug-ins in conjunction with IM systems, the functionality of IM systems may be greatly extended. Specifically, in business applications, such as workflow processes, IM provides a more reliable approach to determining actual delivery of messages.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. application number Ser. No.10/408,341, filed Apr. 7, 2003, which claims the benefit of U.S.provisional patent application Ser. Nos. 60/411,336, filed Sep. 17,2002; 60/416,916, filed Oct. 8, 2002; 60/419,613, filed Oct. 17, 2002;60/426,145, filed Nov. 14, 2002; 60/426,146, filed Nov. 14, 2002;60/426,422, filed Nov. 14, 2002; 60/426,432, filed Nov. 14, 2002; and60/426,440, filed Nov. 14, 2002. These provisional patent applicationsare incorporated herein by reference as if set forth in theirentireties.

U.S. application Ser. No. 10/408,341, filed Apr. 7, 2003, is acontinuation-in-part (CIP) of U.S. patent application Ser. No.10/274,405, filed Oct. 18, 2002, which claims the benefit of U.S.provisional patent application Ser. No. 60/411,336, filed Sep. 17, 2002,and U.S. provisional patent application Ser. No. 60/419,613, filed onOct. 17, 2002.

U.S. application Ser. No. 10/408,341, filed Apr. 7, 2003, is also a CIPof Ser. No. 10/274,408, filed Oct. 18, 2002, which claims the benefit ofU.S. provisional patent application Ser. No. 60/411,336, filed Sep. 17,2002, and U.S. provisional patent application Ser. No. 60/419,613, filedon Oct. 17, 2002.

U.S. application Ser. No. 10/408,341, filed Apr. 7, 2003, is also a CIPof Ser. No. 10/274,478, filed Oct. 18, 2002, which claims the benefit ofU.S. provisional patent application Ser. No. 60/411,336, filed Sep. 17,2002, and U.S. provisional patent application Ser. No. 60/419,613, filedon Oct. 17, 2002.

U.S. Application Ser. No. 10/408,341, filed Apr. 7, 2003, is also a CIPof Ser. No. 10/368,099, filed Feb. 18, 2003, which claims the benefit ofU.S. provisional patent application Ser. No. 60/419,613, filed Oct. 17,2002, which is entirely incorporated herein by reference.

All of these patent applications are incorporated herein by reference asif set forth in their entireties.

FIELD OF INVENTION

The present invention relates generally to the Internet and, moreparticularly, to instant messaging (IM).

BACKGROUND

Currently, instant messaging (IM) systems permit real-timecommunications between users. Typically, the real-time communicationsinclude text messaging, voice chat, and video conferencing. While thetext messaging, voice chat, and video conferencing may be sufficient forcertain interactions between users, these modes provide relativelylimited functionality for other applications.

Thus, a heretofore-unaddressed need exists in the industry to extend thefunctionality of IM systems.

SUMMARY

The present disclosure provides systems and methods for extendingfunctionality of instant messaging (IM) systems.

Briefly described, in architecture, one embodiment of the systemcomprises a workflow transport-protocol object (TPO) and an IM server.The workflow TPO is adapted to receive workflow requests from a workflowserver and format the workflow requests to generate an IM request datastream. In one embodiment, the workflow TPO is further adapted to conveythe IM request data stream to the IM server. The IM server is adapted toreceive the conveyed IM request data stream from the workflow TPO andconvey the IM request data stream to an IM client.

Another embodiment of the system comprises an IM client and a workflowplug-in. The IM client is adapted to receive a workflow request. Theworkflow plug-in is adapted to process the workflow request.

The present disclosure also provides methods for extending functionalityof IM systems. In this regard, one embodiment of the method comprisesthe steps of receiving a workflow request, which is directed to aspecified IM address, from a workflow server and formatting the receivedworkflow request to generate an IM data stream.

Another embodiment of the method comprises the steps of receiving aworkflow request at an IM client, determining if the IM client isregistered with a workflow plug-in, and executing the workflow plug-inin response to determining that the IM client is registered with theworkflow plug-in.

Other systems, methods, features, and advantages will be or becomeapparent to one with skill in the art upon examination of the followingdrawings and detailed description. It is intended that all suchadditional systems, methods, features, and advantages be included withinthis description.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the disclosure can be better understood with referenceto the following drawings. The components in the drawings are notnecessarily to scale, emphasis instead being placed upon clearlyillustrating the principles of the present invention. Moreover, in thedrawings, like reference numerals designate corresponding partsthroughout the several views.

FIG. 1 is a block diagram showing a client-server environment having aninstant messaging (IM) client with extended functionality residing on aworkstation.

FIG. 2 is a block diagram showing components of the workstation of FIG.1 in greater detail.

FIG. 3 is a block diagram showing one embodiment of the IM client ofFIG. 1 having extended functionality.

FIGS. 4 through 7 are data flow diagrams showing embodiments of methodsfor extending IM functionality, which may be performed by the systems ofFIGS. 3A or 3B.

FIG. 8 is a block diagram showing one embodiment of the IM client ofFIG. 1 that is specifically configured to incorporate workflowfunctionality.

FIGS. 9 through 17 are data flow diagrams showing embodiments of methodsfor extending IM functionality, which may be performed by the system ofFIG. 8.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Reference is now made in detail to the description of the embodiments asillustrated in the drawings. While several embodiments are described inconnection with these drawings, there is no intent to limit theinvention to the embodiment or embodiments disclosed herein. On thecontrary, the intent is to cover all alternatives, modifications, andequivalents.

FIG. 1 is a block diagram showing a client-server environment having aninstant messaging (IM) client 130 with extended functionality. The IMclient 130 resides on a workstation 140. As shown in FIG. 1, in oneembodiment, the workstation 140 is connected to the Internet 150, whichserves as a backbone for communication between the workstation 140 andserver-side hardware 160. As is known, the server-side hardware 160 maybe connected to the Internet through a digital subscriber line (DSL)service, an integrated services digital network (ISDN) service, ananalog dial-up service, Ethernet, T-1, or any other service fortransmitting data through a network. Since connections to the Internet150 are known in the art, further discussion of such connections isomitted here. The workstation 140 may also be connected to the Internetthrough similar connections. In one embodiment, the server-side hardware160 is adapted to run an IM server 170 and a plug-in server 180. Thus,in operation, when the user logs in at the IM client 130, acommunication pathway is established between the IM client 130 and theIM server 170. The communication pathway permits server-mediated IMsessions or access to other IM server functions by the IM client 130,though server interaction is not necessarily included in allcommunications for some embodiments.

FIG. 2 is a block diagram showing components of the workstation 140 ingreater detail. As shown in FIG. 2, one embodiment of the workstation140 comprises a processor 210, memory 230, which may be volatile memory,nonvolatile memory, or a combination of both, a network interface 250,and a hardware interface 260, which are all interconnected through alocal bus 220. The hardware interface 260 is adapted to interfaceexternal components, such as a display device 270, to the bus 220. Thenetwork interface 250 is adapted to interface the workstation 140 to theInternet 150 through connection 145 as shown in FIG. 1. The embodimentof FIG. 2 shows the IM client 130 loaded in memory 230. Thus, theworkstation 140 is adapted to engage in IM communications. It should,however, be appreciated that the workstation 140 may be adapted foradditional functions, such as Internet-based game playing or executionof other interactive software (not shown). The memory also includes alisting of installed plug-ins 135 and an operating system 240. In oneembodiment, the listing of installed plug-ins 135 is configured as apredefined directory in which the installed plug-ins are stored. Sincethe IM client 130 provides greater functionality and versatility than astandard web browser, plug-ins for the IM client 130 are preferablystored in a separate listing from the plug-ins for web browsers. In anexample embodiment, the IM plug-ins are component object model (COM)objects that are downloadable from the plug-in server 180 (FIG. 1). Inthis regard, for a Windows™-based system, a plug-in may be a COM objectthat registers a globally-unique identifier (e.g., a CLSID key thatidentifies the COM object) in the Windows™ registry under a directory in“HKEY_LOCAL_MACHINE/SOFTWARE/.” The CLSID key identifies the COM objectthat exports the plug-in interface for use by the IM client 130. SinceCOM objects and CLSID keys are known to those of skill in the art,further discussion of COM objects and CLSID keys are omitted here. Itis, however, sufficient to note that, once the IM client 130 isregistered with a particular plug-in, the plug-in may be launched by theIM client 130 to process incoming data associated with the plug-in.Greater details of the operation of the plug-in are discussed below. Itshould be appreciated that a helper application, which is a separate,free-standing software application, may be used in lieu of a plug-in.Thus, it should be appreciated that the following discussion of plug-insis also applicable to helper applications, as well as otherimplementations for providing extended functionality.

FIG. 3A is a block diagram showing one embodiment of the IM client 130.FIG. 3A also conceptually illustrates the connection between the IMclient 130, the IM server 170, the plug-in server 180, and a database190. The plug-in server 180 comprises one or more downloadable plug-ins390, which are adapted to extend the functionality of the IM client 130.The downloadable plug-ins 390 may include data encryption and decryptionsoftware, specifically-configured Internet web pages, workflowapplications, video games (both interactive and non-interactive),digital audio recorders and players, digital video recorders andplayers, etc. The IM client 130 comprises a parser 310, plug-in searchlogic 315, an index of registered plug-ins 320, which is correlated tothe plug-ins in the listing of installed plug-ins 135, plug-in downloadlogic 325, plug-in installation logic 330, and plug-in execution logic335.

In an example embodiment, when the IM client 130 is initially launched,plug-in search logic 315 in the IM client 130 searches the predefinedplug-in directory 135 to determine which plug-ins are installed in theplug-in directory 135. The installed plug-ins are then registered forsubsequent access. Once the IM client 130 is engaged in aserver-mediated IM session, the IM client 130 may receive a data streamfrom the IM server 170. The parser 310 parses the received data streamfor an application identifier, which, in some embodiments, is anextensible markup language (XML) tag. In one embodiment, the applicationidentifier may be an XML tag that is correlated to a specific plug-in.For example, the XML tag may identify that the incoming data stream is adigital audio stream, which is to be processed by a digital audioplayer. Similarly, the XML tag may identify that the incoming datastream is an encrypted data stream, which is to be decrypted by adecryption application. In another embodiment, the applicationidentifier may be a generic tag that has data of a specificmulti-purpose Internet mail extension (MIME)-type, which is correlatedto a particular application. In that embodiment, the generic tag may beparsed to locate the MIME extension and relate the MIME extension to aspecific plug-in.

Once the parser 310 has identified the plug-in, the IM client 130preferably determines whether or not that plug-in has been registered.If that plug-in has been registered, then the plug-in execution logic335 launches the plug-in 350. In one embodiment, the launching of theplug-in 350 includes a loading of the plug-in into memory 230,initializing the plug-in, and creating a new instance of the plug-in atthe IM client 130. In this regard, multiple instances of a plug-in maybe loaded by the IM client 130. As shown in this embodiment, the lifecycle of the plug-in is determined by the IM client 130. In this regard,when the IM client 130 shuts down, then the plug-in 350 also shuts down.Conversely, if a helper application is launched, then the life cycle ofthe helper application need not be governed by the IM client 130. Sincelife cycle management of plug-ins and helper applications is known tothose of skill in the art, further discussion of life cycle managementis omitted here.

If the IM client 130 determines that the plug-in has not beenregistered, then the plug-in download logic 325 downloads the plug-in350 from the plug-in server 180, and the plug-in installation logic 330installs the plug-in 350 at the predefined listing. Upon installing theplug-in 350, the IM client registers the plug-in 350 as described above.The registered plug-in 350 is then launched by the plug-in executionlogic 335.

FIGS. 4 through 7 are data flow diagrams showing embodiments of methodsfor extending IM functionality. As shown in FIG. 4, one embodiment ofthe method begins when an IM client 130 receives (402) an IM datastream. The embodiment of FIG. 4 shows the IM data stream being receivedfrom an IM server 170. However, it should be appreciated that, in apeer-to-peer environment, the IM data stream may be directly receivedfrom another IM client (not shown). The IM client 130 parses (404) theIM data stream for an application identifier. In some embodiments, theapplication identifier may be a plug-in tag that specifies a particularplug-in, while, in another embodiment, the application identifier may bea generic tag that includes data of a particular MIME type, which isregistered for a particular plug-in. Upon parsing (404) the IM datastream, the IM client 130 determines (406) the particular plug-in thatis associated with the application identifier. For example, if the tagindicates that the data is a digital audio stream, then the IM client130 determines a digital audio player plug-in to be the proper plug-in.Similarly, if the tag indicates that the data is an incoming workflowrequest, then the IM client 130 determines that a workflow applicationis the proper plug-in. Upon determining (406) the proper plug-in, the IMclient 130 further determines (408) whether or not it is registered withthe plug-in. If the IM client 130 is not registered with the plug-in,then the process continues to FIG. 5. Alternatively, if the IM client130 is registered with the plug-in, then the process continues to FIG.6.

As shown in FIG. 5, if the IM client 130 is not registered with theplug-in, then the IM client 130 issues (502) a request for the plug-into a plug-in server 180. In one embodiment, the plug-in server 180 maybe configured such that all of the plug-ins at the plug-in server 180are publicly accessible to every IM user who requests a plug-in. Inanother embodiment, the IM system may be configured so that IM usershave different access levels for different plug-ins. For example, adigital audio player plug-in may be accessible to all IM users while adigital video plug-in may only be accessible to specified IM users. Inanother example, a workflow plug-in may only be accessible to those IMusers who are authorized participants designated by a workflow server.Similarly, an interactive game plug-in may only be accessible to thoseIM users who have subscribed to the interactive game.

In the embodiment where different IM users have different access levels,the issued (502) request may include an access code or an electroniccertificate indicating an authorized download. Since many differentapproaches to restricting downloads are known to those of skill in theart, further discussion of authorized downloads is omitted here. Oncethe request has been issued (502) by the IM client 130, the plug-inserver 180 receives (504) the request for the plug-in and determines(506) whether or not the request includes an authorization to downloadthe plug-in. In one embodiment, this may be done by comparing a receivedaccess code with a database having a list of approved access codes. Oncethe plug-in server 180 has determined (506) that the download isauthorized, then the plug-in server 180 conveys (508) the appropriateinstallable plug-in to the IM client 130. The IM client 130 receives(510) the installable plug-in and installs (512) the plug-in. Theinstalled (512) plug-in is then registered (514). In one embodiment, theplug-in is registered as a COM object in the Windows™ registry under adirectory in “HKEY_LOCAL_MACHINE/SOFTWARE/.”

As shown in FIG. 6, once the proper plug-in has been registered, the IMclient 130 launches (602) the plug-in 350 by loading the plug-in 350into memory, initializing the plug-in 350, and creating an instance ofthe plug-in 350 at the IM client 130. The IM client 130 then conveys(604) to the plug-in 350 any data that may be delineated by theapplication identifiers in the received data streams. The plug-in 350receives (606) the data and executes (608) a function defined by theplug-in with the data to generate a result. For example, if the data isa digital audio stream, then the plug-in may play the digital audiostream. Similarly, if the data is part of an interactive video game,then the plug-in may provide a gaming environment.

If the plug-in is part of an interactive software application (e.g.,workflow application, interactive video game, Internet-basedconferencing, etc.), then the result may be a prompt for feedback from auser at the IM client 130. In this regard, if the plug-in is aninteractive program, then the process may continue to FIG. 7, where theplug-in receives (702) input from a user. Upon receiving (702) theinput, the plug-in conveys (704) data, which is indicative of the input,to the IM client 130. The IM client 130 receives (706) the data andstructures (708) the data so that it may be transmitted using an IMmessage. The structured data is then conveyed (708) to the IM server170. Again, while the embodiment of FIGS. 4 through 7 show aserver-mediated IM process, it should be appreciated that the describedmethods are equally applicable in peer-to-peer IM processes.

FIG. 8 is a block diagram showing another embodiment of the IM client130 of FIG. 1. The IM client 130 of FIG. 8 is specifically configured toincorporate workflow functionality. As shown in FIG. 8, one embodimentof the system includes an IM client 130 in communication with an IMserver 170 through an IM transport protocol object (TPO) 830. In thisregard, the IM TPO 830 is adapted to receive messages from the IM server170 and convey the received messages to the IM client 130. Similarly,the IM TPO 830 is adapted to receive messages from the IM client 130 andconvey the received messages to the IM server 170. Since the behavior ofthe IM TPO 830 is described in greater detail in the above-referencedapplications, further discussion of the IM TPO 830 is omitted here.However, it should be appreciated that the IM TPO 830 is configured sothat messages generated by the IM client 130 are reformatted forcompatibility with the IM server 170, and vice versa.

The system of FIG. 8 also includes a workflow server 810 incommunication with the IM server 170 through a workflow TPO 820. Theworkflow server 810 is adapted to control workflow processes 814 andmanage workflow participants 812 that are associated with the variousworkflow processes 814. In this regard, the workflow server 170generates workflow requests and receives responses to the requests inaccordance with the workflow processes 814. Similar to the IM TPO 830,the workflow TPO 820 provides compatibility between the IM server 170and the workflow server 810. Since the workflow server 810 may use aprotocol that is incompatible with IM, the workflow TPO 820 translatesmessages generated by the workflow server 810 into IM-compatiblemessages. Similarly, the workflow TPO 820 translates IM messagesgenerated by the IM server 170 into a protocol that is compatible withthe workflow server 810.

The system of FIG. 8 further comprises a plug-in server 180 havingvarious downloadable plug-ins 390 including a workflow plug-in 850. Theplug-in server 180 is coupled to the IM client 130, thereby permittingthe IM client 130 to download appropriate plug-ins from the plug-inserver 180. The workflow server 810, the IM server 170, and the plug-inserver 180 are coupled to a database 190. The database 190 may includean access code as described with reference to FIG. 5.

In operation, the workflow server 810 generates a workflow requestidentifying a particular workflow participant (e.g., an IM address of aworkflow participant). The workflow request is relayed to the workflowTPO 820, which queries the IM server 170 to determine whether or not theworkflow participant is present. In other words, for example, theworkflow TPO 820 determines whether the IM address of the workflowparticipant indicates that the workflow participant is online. If theworkflow participant is present, then the workflow TPO 820 reformats theworkflow request into an IM-compatible message and conveys theIM-compatible message to the IM server 170. The IM server 170 relays theIM-compatible message to the IM TPO 830, which translates theIM-compatible message into a workflow request that is compatible withthe IM client 130. The translated workflow request is relayed message tothe IM client 130. The IM client 130 receives the translated workflowrequest and launches a workflow plug-in 850 to process the translatedworkflow request by, for example, prompting the workflow participant fora response. If the workflow participant responds to the request, thenthe response is conveyed from the workflow plug-in 850 to the IM client130. The IM client 130 relays the response to the IM TPO 830, whichtranslates the response into an IM-compatible message. The IM-compatiblemessage is conveyed to the IM server 130, which further relays theIM-compatible message to the workflow TPO 820. The workflow TPO 820reformats the response into the protocol of the workflow server 810 andconveys that response to the workflow server 810.

As seen from the embodiment of FIG. 8, employing an IM system to conveyworkflow requests and responses results in fewer false-deliverymessages. In other words, unlike email-based workflow processes in whichonly delivery confirmation of the email is generally possible, theIM-based workflow process provides real-time notification as to whetheror not the workflow participant received a request by deliveringrequests to the participant after verifying that the participant ispresent. Thus, by delivering a workflow request to only those workflowparticipants who are present, the system of FIG. 8 provides a moreaccurate and efficient confirmation of delivery than workflow processesthat utilize email. Several embodiments of IM-based workflow processesare described with reference to FIGS. 9 through 17.

FIGS. 9 through 17 are data flow diagrams showing embodiments of methodsfor extending IM functionality. As shown in FIG. 9, one embodiment ofthe process begins when a workflow server 810 generates (902) a workflowrequest for a selected IM address for a workflow participant. Thegenerated (902) workflow request is conveyed (904) from the workflowserver 810 to a workflow TPO 820, which receives (906) the workflowrequest and queries (908) an IM server 170 to determine whether or notthe selected IM address is present on the network. The IM server 170receives (910) the query and returns (912) a result to the workflow TPO820. The workflow TPO 820 receives (914) the result and evaluates (916)the result for presence of the selected IM address. If the resultindicates that the selected IM address is present on the network, thenthe process continues to FIG. 11. If, on the other hand, the resultindicates that the selected IM address is not present on the network,then the process continues to FIG. 10.

As shown in FIG. 10, if the selected IM address is not present, then theworkflow TPO 820 generates (1002) a not-present message and conveys(1004) the not-present message to the workflow server 810. The workflowserver 810 receives (1006) the not-present message and selects (1008)another IM address related to the workflow participant. Once another IMaddress has been selected (1008), the process returns to FIG. 9.

If the selected IM address is present on the network, then the workflowTPO 820 reformats (1102) and tags the workflow request, as shown in FIG.11, so that the workflow request is IM compatible. In one embodiment,the workflow request is tagged with an extensible markup language (XML)tag, which indicates that the request is a workflow request. In anotherembodiment, the workflow request is tagged with a generic XML tag, whichindicates that a particular workflow-related message is embedded in theworkflow request. In either event, the tagged workflow request isconveyed (1104) to the IM server 170. The IM server 170 receives (1106)the tagged workflow request and relays (1108) the tagged workflowrequest to an IM TPO 830. The IM TPO 830 receives (1110) the taggedworkflow request and translates (1112) the workflow request for an IMclient 130. The translated workflow request is relayed (1114) to the IMclient 130, which receives (1116) the translated workflow request.

The process continues to FIG. 12 where the IM client 130 parses (1202)the translated workflow request for the particular tags (e.g., XMLworkflow tags). Upon parsing (1202) the workflow request, the IM client130 determines (1204) from the parsed tags that a workflow plug-in isthe appropriate plug-in for processing the received workflow request.Upon determining (1204) that the workflow plug-in is the appropriateplug-in, the IM client 130 further determines (1206) whether or not theIM client 130 is registered with the workflow plug-in. Since theregistering of the IM client 130 with plug-ins is described above,further discussion of registering IM clients is omitted here.

If the IM client 130 determines (1206) that the IM client 130 isregistered with the workflow plug-in, then the process continues to FIG.14. However, if the IM client 130 determines that the IM client 130 isnot registered with the workflow plug-in, then the process continues toFIG. 13.

As shown in FIG. 13, if the IM client 130 is not registered with theworkflow plug-in, the IM client 130 issues (1302) a request to a plug-inserver 180 for the workflow plug-in. In one embodiment, the system maybe configured so that only authorized users or participants may retrievethe workflow plug-in. In another embodiment, the workflow plug-in may beaccessible to all users that request the workflow plug-in. If onlyauthorized participants are permitted access to the workflow plug-in,then the plug-in server 180 receives (1304) the request and determines(1306) whether or not the request includes authorization to retrieve (ordownload) the workflow plug-in. If it is determined (1306) that thedownload is authorized, then the plug-in server 180 conveys (1308) theworkflow plug-in to the IM client 130. The IM client 130 receives (1310)the workflow plug-in, installs (1312) the workflow plug-in, andregisters (1314) the IM client 130 with the installed workflow plug-in.

As shown in FIG. 14, when the IM client 130 is registered with theworkflow plug-in, the IM client 130 creates (1402) an instance of theworkflow plug-in 850. Upon creating (1402) the instance of the workflowplug-in 850, the IM client conveys (1404) data that is delineated by thetags in the workflow request to the workflow plug-in 850. The workflowplug-in receives (1406) the data and processes the data. In oneembodiment, the processing of the data includes the step of prompting(1408) a user for a response to the received data.

If a user is prompted (1408) for a response and the user provides aresponse, then the process continues to FIG. 15 where the workflowplug-in 850 receives (1502) the workflow response from the user andconveys (1504) the workflow response to the IM client 130. The IM clientreceives (1506) the workflow response and relays (1508) the workflowresponse to the IM TPO 830. The IM TPO 830 receives (1510) the workflowresponse and the process continues to FIG. 16.

As shown in FIG. 16, the IM TPO 830, upon receiving (1510) the workflowresponse from the IM client 130, translates (1602) the workflow responseinto an IM-compatible workflow response. The translated workflowresponse is conveyed (1604) to the IM server 170. The IM server 170receives (1606) the translated workflow response and relays (1608) thetranslated workflow response to the workflow TPO 820. The workflow TPO820 receives (1610) the translated workflow response and reformats(1612) the translated workflow response into the protocol of theworkflow server 810.

The process continues to FIG. 17 where the workflow TPO 820 conveys(1702) the reformatted workflow response to the workflow server 810. Theworkflow server 810 receives (1704) the reformatted workflow responseand determines (1706) whether or not additional workflow processesshould be executed. If it is determined (1706) that additional workflowprocesses should be executed, then the process returns to FIG. 9. If, onthe other hand, it is determined that no additional workflow processesare to be executed, then the process ends.

As shown with reference to FIGS. 9 through 17, by employing IM to conveyworkflow messages, the presence aspect of IM may be used to moreaccurately confirm delivery of workflow requests. Additionally, byemploying IM, which is substantially a real-time mode of communication,workflow processes may be accelerated. In other words, unlike priorsystems employing email in which a reply may be significantly delayed,the IM-based workflow process is a more streamlined process.

The IM client 130, the parser 310, the plug-in search logic 315, theplug-in download logic 325, the plug-in installation logic 330, theplug-in execution logic 335, the plug-in 350, the workflow plug-in 850,and the downloadable plug-ins 390 of the present invention can beimplemented in hardware, software, firmware, or a combination thereof.In the preferred embodiment(s), the IM client 130, the parser 310, theplug-in search logic 315, the plug-in download logic 325, the plug-ininstallation logic 330, the plug-in execution logic 335, the plug-in350, the workflow plug-in 850, and the downloadable plug-ins 390 areimplemented in software or firmware that is stored in a memory and thatis executed by a suitable instruction execution system. If implementedin hardware, as in an alternative embodiment, the IM client 130, theparser 310, the plug-in search logic 315, the plug-in download logic325, the plug-in installation logic 330, the plug-in execution logic335, the plug-in 350, the workflow plug-in 850, and the downloadableplug-ins 390 can be implemented with any or a combination of thefollowing technologies, which are all well known in the art: a discretelogic circuit(s) having logic gates for implementing logic functionsupon data signals, an application specific integrated circuit (ASIC)having appropriate combinational logic gates, a programmable gatearray(s) (PGA), a field programmable gate array (FPGA), etc.

Any process descriptions or blocks in flow charts should be understoodas representing modules, segments, or portions of code which include oneor more executable instructions for implementing specific logicalfunctions or steps in the process, and alternate implementations areincluded within the scope of the preferred embodiment of the presentinvention in which functions may be executed out of order from thatshown or discussed, including substantially concurrently or in reverseorder, depending on the functionality involved, as would be understoodby those reasonably skilled in the art of the present invention.

The processes of FIGS. 4 through 7 and FIGS. 9 through 17 may beexecuted by computer code comprising an ordered listing of executableinstructions for implementing logical functions. In this regard, thecomputer code may be embodied in any computer-readable medium for use byor in connection with an instruction execution system, apparatus, ordevice, such as a computer-based system, processor-containing system, orother system that can fetch the instructions from the instructionexecution system, apparatus, or device and execute the instructions. Inthe context of this document, a “computer-readable medium” can be anymeans that can contain, store, communicate, propagate, or transport theprogram for use by or in connection with the instruction executionsystem, apparatus, or device. The computer-readable medium can be, forexample but not limited to, an electronic, magnetic, optical,electromagnetic, infrared, or semiconductor system, apparatus, device,or propagation medium. More specific examples (a nonexhaustive list) ofthe computer-readable medium would include the following: an electricalconnection (electronic) having one or more wires, a portable computerdiskette (magnetic), a random access memory (RAM) (electronic), aread-only memory (ROM) (electronic), an erasable programmable read-onlymemory (EPROM or Flash memory) (electronic), an optical fiber (optical),and a portable compact disc read-only memory (CDROM) (optical). Notethat the computer-readable medium could even be paper or anothersuitable medium upon which the program is printed, as the program can beelectronically captured, via for instance optical scanning of the paperor other medium, then compiled, interpreted or otherwise processed in asuitable manner if necessary, and then stored in a computer memory.

Although exemplary embodiments have been shown and described, it will beclear to those of ordinary skill in the art that a number of changes,modifications, or alterations may be made, none of which depart from thespirit of the present invention. For example, while the preferredembodiments illustrate plug-ins that are created and destroyed by the IMclient, it should be appreciated that IM functionality may be extendedby using helper applications that are executed as separate,free-standing applications. Additionally, while a specific embodiment ofa workflow plug-in is shown with reference to FIGS. 8 through 17, itshould be appreciated that a video game plug-in, an audio plug-in, avideo plug-in, or any number of other applications may be implementedusing the systems and processes described above. Specifically, it shouldbe appreciated that the embodiments described above are particularlyconducive to interactive applications such as interactive video games orinteractive business applications. In this regard, it should beappreciated that the above-described approaches may be extended to anyapplication that is amenable to interaction by multiple users.

All such changes, modifications, and alterations should therefore beseen as within the scope of the present invention.

1. A communication method comprising: receiving a workflow request at aninstant messaging (IM) client; determining if the IM client isregistered with a workflow plug-in in response to receiving the workflowrequest; and executing the workflow plug-in in response to determiningthat the IM client is registered with the workflow plug-in.
 2. Themethod of claim 1, further comprising: receiving an input at the IMclient, the input being indicative of a response to the workflowrequest; generating a workflow response from the received input; andconveying the workflow response.
 3. The method of claim 1, furthercomprising downloading a workflow plug-in from a plug-in server inresponse to determining that the IM client is not registered with theworkflow plug-in.
 4. The method of claim 3, further comprising storingthe downloaded workflow plug-in.
 5. The method of claim 3, furthercomprising registering the IM client with the downloaded workflowplug-in.
 6. The method of claim 3, wherein downloading the workflowplug-in comprises providing authentication information to the plug-inserver for authentication by the plug-in server.
 7. The method of claim6, further comprising receiving the workflow plug-in from the plug-inserver in response to the plug-in server authenticating theauthentication information.
 8. A communication system comprising: afirst receiving component configured to receive a workflow request at aninstant messaging (IM) client; a determining component configured todetermine if the IM client is registered with a workflow plug-in inresponse to receiving the workflow request; and an executing componentconfigured to execute the workflow plug-in in response to determiningthat the IM client is registered with the workflow plug-in.
 9. Thesystem of claim 8, further comprising: a second receiving componentconfigured to receive an input at the IM client, the input beingindicative of a response to the workflow request; a generating componentconfigured to generate a workflow response from the received input; anda conveying component configured to convey the workflow response. 10.The system of claim 8, further comprising a downloading componentconfigured to download a workflow plug-in from a plug-in server inresponse to determining that the IM client is not registered with theworkflow plug-in.
 11. The system of claim 10, further comprising astoring component configured to store the downloaded workflow plug-in.12. The system of claim 10, further comprising a registering componentconfigured to register the IM client with the downloaded workflowplug-in.
 13. The system of claim 10, wherein the downloading componentis further configured to provide authentication information to theplug-in server for authentication by the plug-in server.
 14. The methodof claim 13, further comprising a third receiving component configuredto receive the workflow plug-in from the plug-in server in response tothe plug-in server authenticating the authentication information.
 15. Acomputer readable storage medium for facilitating communications,comprising: first receiving logic configured to receive a workflowrequest at an instant messaging (IM) client; determining logicconfigured to determine if the IM client is registered with a workflowplug-in in response to receiving the workflow request; and executinglogic configured to execute the workflow plug-in in response todetermining that the IM client is registered with the workflow plug-in.16. The computer readable storage medium of claim 15, furthercomprising: second receiving logic configured to receive an input at theIM client, the input being indicative of a response to the workflowrequest; generating logic configured to generate a workflow responsefrom the received input; and conveying logic configured to convey theworkflow response.
 17. The computer readable storage medium of claim 15,further comprising downloading logic configured to download a workflowplug-in from a plug-in server in response to determining that the IMclient is not registered with the workflow plug-in.
 18. The computerreadable storage medium of claim 17, further comprising storing logicconfigured to store the downloaded workflow plug-in.
 19. The computerreadable storage medium of claim 17, further comprising registeringlogic configured to register the IM client with the downloaded workflowplug-in.
 20. The computer readable storage medium of claim 15, furthercomprising: providing logic configured to provide authenticationinformation to the plug-in server for authentication by the plug-inserver; and a third receiving component configured to receive theworkflow plug-in from the plug-in server in response to the plug-inserver authenticating the authentication information.